Method and system for directed documentation of construction projects

ABSTRACT

Methods and systems for directed creation of construction documentation are provided. Example embodiments provide a Directed Documentation System (a “DDS”), which directs, in a computer-assisted manner, the creation of a historical record of a portion or an entire construction project. In one embodiment, the DDS comprises a directed construction data organization process/component, a directed documentation data acquisition process/component, a construction documentation data retrieval process/component, and a construction documentation data distribution process/component. These components cooperate to direct the documentation of a construction project in a manner that insures that all desired aspects of the project are documented thoroughly and uniformly. This abstract is provided to comply with rules requiring an abstract, and it is submitted with the intention that it will not be used to interpret or limit the scope or meaning of the claims.

TECHNICAL FIELD

The present disclosure relates to methods, processes, and systems fordocumenting aspects of a construction process and, in particular, tomethods, processes, and systems for integrating images and textautomatically with other documentation of a construction projectaccording to a process directed by a documentation system.

BACKGROUND

Construction projects present major complications to the ability toaccurately assess time, progress, and quality at all stages and tasks ofa project. This phenomenon is partially due to the inherent nature ofconstruction to permanently cover earlier work. Critical elements arecontinually covered and increasingly inaccessible after the fact. If thework relating to a particular task is not assessed at the right momentin time, it may become impossible to assess. Furthermore, the pace andmulti-disciplined subcontracting approach of modern construction leadsto numerous simultaneous tasks, which makes tracking each task at thecorrect time all the more challenging.

The difficulty in determining the conditions and exact time frames inwhich each task is completed, especially in a large constructionproject, is an industry wide challenge. These determinations areimportant in defining payment schedules, code compliance, legal claimslegitimacy, quality control, and maintenance procedures. Betterdeterminations can lead to early corrections of design issues, fewermisunderstandings, better compliance with codes, cost containment, andthe like.

The industry has evolved numerous ways to track and control informationsurrounding construction. Such information may include condition andprogress information, for example, what dates and times particularactivities or tasks have been performed; who has performed them; whetherthey have been performed as specified by the construction documents, forexample, using specified materials, techniques, etc.; what adjustmentshave been made that diverge from the plans; whether the activity or taskis complete, or the portion completed; etc. Traditionally, thesetracking methods center around written paper reports that are disciplinespecific received from sub-contractors, which are manually compiled bythe general contractor (or other personnel in charge) and then submittedto the owner. Often owners engage their own representative to observeand report on the condition and progress of a project as it isprogressing. Current commercially available construction managementsoftware endeavors to track and combine many different types oftraditional paper documents into one system. However, there is nomechanism for insuring who's view of the world is correct.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of logical components an example DirectedDocumentation System.

FIG. 2 is an example block diagram of an overview of the documentationand feedback processes used by an example Directed Documentation Systemto direct and insure the acquisition of timely documentation data.

FIG. 3 is an example block diagram of the example inputs to and outputsgenerated by a directed construction data organization component of aDirected Documentation System.

FIG. 4 is an example flow diagram of a process used by the directedconstruction data organization component to organize construction dataso that it can be scheduled for timely and accurate documentation.

FIG. 5 is an example flow diagram of an example process used to generatea documentation schedule from construction contract document data.

FIG. 6 is an example flow diagram of a process used by an exampleDirected Documentation System to direct the timely and accuratedocumentation of a construction project.

FIGS. 7A-7C are example screen displays of a list view of an exampledirected documentation data viewer.

FIGS. 8A-8B are example screen displays of a detail view of an exampleDirected Documentation System data viewer.

FIG. 9 is an example screen display of a selection view of an exampleDirected Documentation System data viewer.

FIG. 10 is an example screen display of a technique for invoking imageview on one or more images selected in list view.

FIG. 11 is an example screen display of an image displayed in responsereceiving a “show image” command along with the commands available tomanipulate the image.

FIG. 12 is an example screen display of using the Directed DocumentationSystem to communicate suggestions to other personnel working on theconstruction project.

FIGS. 13A-13B are example screen displays of the multiple imagepresentation capabilities of an example Directed Documentation Systemdata viewer.

FIGS. 14A-14B are example screen displays of an electronic quickmeasurement tool that can be used to obtain measurements of constructionelements that appear in approximately the same vertical plane as anelement with a known measurement.

FIGS. 15A-15I is an example screen display sequence of using anelectronic calculated measurement tool to measure elements that appearwithin a user defined plane adjusted for perspective.

FIGS. 16A-16B are example screen displays of “as-built” documentationproduced automatically as a result of a Directed Documentation Systemprocess.

FIG. 17 is an example block diagram of a computer-assisted generalpurpose computer system for practicing embodiments of a DirectedDocumentation System.

DETAILED DESCRIPTION

Embodiments described herein provide enhanced computer- andnetwork-assisted methods and systems for comprehensive electronicdocumentation of construction projects that automatically produces avisual and written history of ongoing and completed construction.Example embodiments provide a Directed Documentation System (“DDS”),which enables its users to collect, manage, organize images with otherconstruction contract data to document a construction project in aplanned, more automated fashion. The DDS directs the documentation of aconstruction project in a manner that insures that desired aspects ofthe project are documented thoroughly, using uniform terminology acrossdisciplines within the project, according to a set of well establishedindustry standards, and in a manner that insures the integrity of thedocumentation data. The Directed Documentation System creates for eachproject a unique electronic library of photographic surveys and otherelectronic documents, which are stored in a format that permitsretrieval of both written and photographic detail.

The acquisition of documentation data is directed by a computer-assistedprocess that is adjusted on an ongoing basis to react to the realitiesof construction such as time delays, sub-contractor difficulties, etc.The documentation data acquisition process takes into account acontinually revised documentation schedule and the protocols andparameters introduced into each project initially and in response tochanges that occur and evolve during the construction process. Thiscontinuous and directed data acquisition results in a historical libraryof photographs and other data that documents construction details andtimeframes for each targeted construction activity (one or more tasks)in a manner that is independent from those designing, commissioning, andperforming the tasks. Moreover the documentation data can be verifiedfor content, accuracy, and consistency prior to its integration into anDDS data repository.

The data gathered and integrated into the Directed Documentation Systemcreates a planned record of construction activities, progress,compliance and quality. The DDS data records stored in the DDS datarepository can ultimately provide the core data for pre-conditionsurveys; aid in providing as-built documentation; provide inspectionclarification information, be used for future building operations,maintenance, expansion, and renovation; provide an indisputable recordfor legal claims and claims avoidance, identifies a basis fordetermining fair value of work performed; and provide otherdocumentation such as an historical record, public relations relateddocumentation, etc. However, that the techniques of DirectedDocumentation System may be useful to create a variety of other types ofdocumentation as well. DDS created data can be distributed in hardmedium, over networks and/or through a web browser interface.

In addition, reports based upon DDS created data can be automaticallydistributed electronically, such as by email or other automatic orsemi-automatic feed, at determined time intervals (e.g., monthly), atdetermined construction activity related times (e.g., when a progresspayment is due), at calculated times (e.g., such as every third day),after particular and/or in response to triggering events such asnotifications that are programmed into the documentation schedule andupdated as the construction project progresses (e.g. when an activity issupposed to have been completed under the contract but is observablylate). Reports can be predetermined progress payment reports triggeredby events in the documentation schedule or can be customized to reportproject progress, various aspects of the construction (such aseverything related to drywalling activities or internal plumbing),and/or various features of the construction (such as the West side ofthe building). The distribution of data provides clients with remotemonitoring capabilities by allowing continual and even near real-timemonitoring of progress, changes and refinements to the project. As usedherein, near real-time is relative to the construction—it can meananything from being able to observe the construction as it is beingbuilt (such as when the data acquisition occurs and is downloaded andintegrated almost immediately into a DDS computer system as it is beingacquired) to within days of the activity.

The Direct Documentation System also allows identification of projectwide issues and allows early, collaborative, resolution to problems.Automatic notifications of particular types of discrepancies can alsoaid in early detection and resolution of problems. The DDS can track anddocument to completion all types of construction related issues. Inaddition, the DDS adds an aspect of security to the documentationprocess. For example, chain of custody can be preserved by tracking theordering in which images are captured, modified etc. In someembodiments, the DDS issues two separate media copies of the rawdocumentation data capture, which are sealed as evidence and archivedoffsite. In the event of a lawsuit, a party can prove that the imageswere not retouched or changed out of sequence. The end result ofdirected documentation techniques is that they produce potential benefitin terms of timely contract closeout, overall schedule, costcontainment, system performance and the quality of the finishedconstruction.

FIG. 1 is a block diagram of logical components an example DirectedDocumentation System. The DDS 100 logically comprises five differentcomponents including a project construction and documentation data datarepositiory 101 (also referred to as the DDS repository), a directedconstruction data organization component 102 (also referred to as thedata organization component), a directed documentation data acquisitioncomponent 103 (also referred to as the data acquisition component), aconstruction documentation data retrieval component 104 (also referredto as the retrieval component), and a construction documentation datadistribution component 105 (also referred to as the distributioncomponent). The functionality of these various components may bedistributed differently and/or repeated between the components.

As one can observe from FIG. 1, the construction data as derived fromthe various project contract documents by the data organizationcomponent 102, is stored in the DDS data repository 101. This data isused by the data acquisition component 103 to derive a documentationschedule. The documentation schedule is a continually adjusted detailedwork plan of potentially the entire construction project from start tofinish. This work plan identifies areas that need to be recorded(documented); creates a process to track the documentation of theseareas; registers events that can be used to trigger automaticnotification or reports; registers landmark events such as points in theconstruction where activity completion is to occur. Landmark events maytrigger instructions to the data acquisition instructions to conductverification documentation tasks. Note that as requested by a client,only a portion of the project may be subject to the DDS process, and, inthat case, the documentation schedule reflects the period and/orspecific construction disciplines and/or construction activities to bedocumented.

The documentation schedule reflects the realities of the job—whatconstruction (and documentation) has been actually accomplished andwithin what actual time periods, is reflective of actual fieldconditions, and is adjusted to account for critical path issues—ratherthan simply mirroring the construction schedule. To do this, thedocumentation schedule is adjusted by the DDS 100 as the DDS 100receives input from the field that indicates discrepancies orinformation that somehow conflicts with current entries in thedocumentation schedule. The documentation schedule can be implemented ina computer system using any conventional means that permits activities,descriptions, instructions, and notification triggers to be associatedwith calendared entries.

The documentation schedule (along with other protocols and parameterssuch as uniform terminology) is used to drive and direct the dataacquisition component 103 to produce directed documentation dataacquisition instructions (referred to also as data acquisitioninstructions). For example, such data acquisition instructions may beproduced on a daily basis and given to field personnel to capture imagesand related text or other data to document the project as instructed.Appendix A, incorporated herein by reference in its entirety, is anexample of a portion of such directed documentation data acquisitioninstructions. For each documentation activity, the field (the datacapturer person/entity/device) is provided with a set of “imageryzones,” i.e., aspects to capture as documentation. Note that althoughthis description primarily refers to field personnel as the entityresponsible for acquiring the images and other documentation data, astechnology becomes more and more sophisticated, it is contemplated thatmuch of the directed data acquisition could be accomplished by on-sitecameras, controlled remotely, or by other types of robotics modules.Also, one should note that audio (e.g., voice annotation) could beintegrated into the documentation data in a similar manner to text.

Once the documentation data is acquired it is integrated into the DDSrepository and used to update the documentation schedule. At any time,the construction documentation data in the DDS can be retrieved on aselective basis or explored using, for example, constructiondocumentation data retrieval component 104 such as a DDS viewerdescribed below in detail with respect to FIGS. 7A-16B. In addition, atperiodic times, determined times, or upon request, the data distributioncomponent 105 can be invoked to distributed documentation data stored inthe DDS repository 101 electronically or paper copy.

FIG. 2 is an example block diagram of an overview of the documentationand feedback processes used by an example Directed Documentation Systemto direct and insure the acquisition of timely documentation data. InFIG. 2, the directed construction data organization process 210 takes inthe contract documentation data 201 and a set of protocols andterminology 202 and generated a documentation schedule 203 and stores aset of construction data 204 organized for guiding the documentationprocess. From the schedule 203 and the protocols and terminology 202,the directed documentation data acquisition process 220 produces thedata acquisition instructions 205 on a designated based to direct thecapture of documentation in the field. These are forwardedelectronically or otherwise as appropriate to a data capturer 230 toobserve and document the construction site. The data capturer 230documents the construction project as directed by the instructions 205recording images (digital or otherwise) and associated text, audio, orother types of supplemental data in whatever form it is captured. Thecaptured documentation data 206 is then sent (forwarded, downloaded, orotherwise communicated) to a documentation data input and verificationprocess 240 to be integrated into the DDS data repository. Theverification process may consist of actions such as enhancing the imageusing conventional or proprietary image enhancement software, checkingto make sure that the image makes sense to the associated CSI code andlocation indications, and that the comments inserted by the field makesense. The integrated documentation data 207 is then examined to detectinconsistencies with the documentation (and construction) schedule andthen the schedule is adjusted to accommodate the realities of theconstruction progress, conditions, etc. For example, if the datacapturer has been asked to verify that a construction activity has beencompleted, and the documentation data shows that it is not, then thedocumentation schedule is adjusted to continue to request verificationuntil the activity is complete. Also, potentially, notifications areautomatically distributed, along with the documentation data supportingthe notification, to personnel that have registered an interest inreceiving information with respect to completion of this activity. Thedetection and adjustment process is currently performed manually in anexemplary implementation. However, as text and image recognitionsoftware become more sophisticated and robust, a large portion of suchdetection and schedule adjustments may be able to be performedautomatically by a computer system.

In addition to adjustments made to the documentation schedule, the DDSmay at different times through a process 260 receive notification of achange indication to some aspect of the construction project. Suchnotification may come in many forms, including change orders,architectural supplemental instructions (“ASIs”), and requests forinformation (“RFIs”). When notification of such change indications arereceived, the contract document data 201 are appropriately adjusted (forexample, by inserting copies of the change indication documents into thesystem). These adjustments to the contract documentation data 201 thentrigger the data organization process 210 to adjust the constructiondata 204 and the documentation schedule 203 as appropriate. Then, thenext time data acquisitions instructions 205 are issued, they will takeinto account updates that have been made to the construction data 204and the documentation schedule 203.

FIG. 3 is an example block diagram of the example inputs to and outputsgenerated by a directed construction data organization component of aDirected Documentation System. As described with reference to FIG. 2,the directed construction data organization component 301 receives datarelated to the construction project contract documents and producesseveral different outputs that are used to guide the data acquisitionprocess. In one example embodiment, the contract documents includeconstruction drawings 302, construction specifications 303, authorizedchange indications 304 (e.g., COs—change orders, RFIs, ASIs, inspectionreports/results, etc.), and a construction schedule (including, forexample, critical path indications as needed). The data organizationprocess 301 then organizes this contract data and produces constructionproject related data 306 for documentation use, documentation protocols307 and documentation data terminology 308 as described further below,and a documentation schedule 309. As described with reference to FIG. 2,the outputs 306-309 of the data organization process 301 are used toderive and generate directed documentation data acquisitioninstructions.

Example embodiments described herein provide applications, tools, datastructures and other support to implement a Directed DocumentationSystem to be used for documenting construction projects. Otherembodiments of the described techniques may be used for other purposes,including for evaluation of structure, systems, and contents forpreparation of insurance policies, forensics studies of construction orsystems failures, etc. In addition, the described techniques could beused to create an accurate inspection schedule that is automaticallytransmitted to government building inspectors. Also, DDS documentationdata and reports can be used by oversight authorities to insure thatregulations are being met, etc. In the following description, numerousspecific details are set forth, such as data formats and code sequences,etc., in order to provide a thorough understanding of the describedtechniques. The embodiments described also can be practiced without someof the specific details described herein, or with other specificdetails, such as changes with respect to the ordering of the code flow,different code flows, etc.

Also, although certain terms are used primarily herein, other termscould be used interchangeably to yield equivalent embodiments andexamples. For example, it is well-known that equivalent terms in theconstruction field and in other similar fields could be substituted forsuch terms as “contract documents,” “construction specification,” etc.Also, as used herein, the term “image” is not limited to traditionalphotographs and may include other types of image generation such as timelapse video, thermography (infrared), and X-ray, sonar, and boroscopeimages, etc. Also where the term “text” is used, it is to be understoodthat text includes any data in alphanumeric form, including digital dataand symbols. Also, where text is referred to, audio could also besubstituted or used to supplement the text. In addition, terms may havealternate spellings which may or may not be explicitly mentioned, andall such variations of terms are intended to be included.

FIG. 4 is an example flow diagram of a process used by the directedconstruction data organization component to organize construction dataso that it can be scheduled for timely and accurate documentation. Insteps 401, the data organization process inputs and organizes eitheroriginal or updated (as described with respect to FIG. 2) data from thevarious contract documents 302-305. In step 402, these data are examinedto synthesize (or revise) the documentation schedule. In step 403, theprocess synthesizes terminology and protocols for common and projectbased data as described further below. Then in step 404, the DDS (eitherthrough this process or some other event handling mechanism awaitsupdates to the contract data. When updates are received, the processbegins again in step 401 to process the revised data; otherwise, theprocess continues to wait or be notified of additional changes to theconstruction contract data.

FIG. 5 is an example flow diagram of an example process used to generatea documentation schedule from construction contract document data. Forpurposes of easier explanation, it is assumed that the constructionschedule (or critical path management “CPM” documents) divisions (e.g.,“days) are used to generate the documentation schedule. It is understoodthat other divisions may be similarly incorporated. In step 501, eachday of the construction schedule is examined starting with the first. Instep 502, the process checks to see if there are any more days toprocess and, if not, proceeds with step 505, else continues in steps503. In step 503, the process goes through each aspect of theconstruction project that is scheduled for completion that day, andinserts a “verification event” into the documentation schedule.Verification events are a type of documentation event that can be usedto trigger the insertion of verification instructions into the dataacquisition instructions distributed to the data capturer and to triggerautomatic notifications to construction project related personnel. Inaddition, automatically produced and distributed progress paymentreports may be triggered by verification events. In step 504, for eachaspect of construction or location where work is to be performed, theprocess inserts a documentation event, with sufficient information sothat documentation event instructions can be appropriately generated aspart of the documentation data acquisition instructions. The processthen returns to step 502 to process any remaining days on theconstruction schedule. When the construction schedule is exhausted andno more days remain to be processed, then in step 505 the process addsany additional items to the documentation schedule. For example,specific events that are initiated by the documentation schedule itself(such as tallying numbers of images in different disciplines) are alsoentered into the documentation schedule. Also, other desired eventtriggers are inserted into the documentation schedule. In step 506, thedocumentation schedule is then output in the appropriate manner, such asstored in the DDS data repository.

FIG. 6 is an example flow diagram of a process used by an exampleDirected Documentation System to direct the timely and accuratedocumentation of a construction project. The DDS process loops over thedocumentation schedule to generate a set of documentation dataacquisition instructions that are distributed to a data capturer. Recallthat a data capturer may be a person such as a field representative, butmay also or instead be a system, device, or other type of entity. Morespecifically, in step 601, the process examines the first activitywithin the relevant range in the documentation schedule. The relevantrange may be for example, daily, weekly, monthly, or hourly. Or, if thedocumentation schedule is arranged by discipline, appropriateadjustments are made to the process exemplified by FIG. 6. In step 602,the process determines whether there are more documentation events toprocess, and, if so, continues in step 603, otherwise continues in step605. In step 605, the process generates documentation data acquisitioninstruction(s) for the current documentation event (or verificationevent) being processed. As much as possible, these documentation dataacquisition instructions are generated automatically by a computersystem associated with the DDS, although they may be augmented manually.

Directed documentation data acquisition instructions typically include aset of detailed descriptions of the desired documentation organized bylocation. Other organizations of the instructions can be supported.Appendix A is an example of data acquisition imagery descriptions thatdrive what images the data capturer is responsible to capture. Althoughof course other information or different information can be madeavailable to the data capturer, Appendix A shows for each relevantlocation as determined by the documentation schedule, a “subject” thatis to be documented along with a checklist to make sure certain aspectsof the construction are captured, and one or more Construction StandardsInstitute (“CSI”) codes for indexing the information. Note that thedescriptions are provided as part of a checklist, in which locationchecklists can be expanded or collapsed for presentation purposes usingconventional spreadsheet techniques. Other techniques for presenting theinformation can also be used. Each location is typically specified by aprimary location, augmented by one or more sub-locations. An examplelisting of CSI codes that can be used for instruction and indexingpurposes is included as Appendix B, which is incorporated herein byreference in its entirety.

Directed documentation data acquisition instructions also typicallyinclude a set of protocols that may be common across multipleconstruction projects or that may be specific to the project at hand.These protocols include additional general instructions to the field forcapturing images. For example, the data acquisition instructionstypically instruct the data capturer to always look out for and recordthe following items:

-   -   things that should be done in a particular manner in any        construction project based upon industry “know-how” (e.g.,        “dewatering wells should always pump to filtration tanks”);    -   all physical activity—what do you see happening in various        locations;    -   all equipment being used—to the level of manufacturer, model,        etc.;    -   notable site conditions (e.g., weather, acts of god; noticed        delays, things being done that aren't in the construction        schedule, etc.);    -   all people on site—who and how many;    -   all material being used to the level of manufacturer, part        numbers, etc.;    -   notable bad quality issues (e.g., insulation has been installed        that doesn't reach all the way to the roof); and    -   documentation techniques, such as a detail or close-up is always        accompanied by a long shot to establish reference for the end        user.        Example guidelines, particular based upon industry “know-how”        are shown in Appendix C, which is incorporated herein by        reference in its entirety. Other protocols can be incorporated        as needed into any implementation of the data acquisition        instructions.

Note as well that all of the data acquisition instructions, includingthe imagery descriptions and the protocols, are communicated using a setof uniform terminology. Typically, the terminology includes someterminology that is common across the entire DDS—such as namingconventions for what orientation should be used to capture an image—andsome terminology that may be project specific—such as the names ofvarious sub-locations (“tower A”). For example, common terminology mayinclude that “elevation” is a head-on view (e.g., a side of a building)that corresponds to elevations in the construction drawings; “details”correspond to the detail boxes on construction drawings; and directionoverview commands such as “west overview” or “east overview” correspondsto taking an image looking in the requested direction; and “plan”corresponds to construction drawings and reflects capturing an imagefrom above.

Returning to FIG. 6, in step 604, the data acquisition instructions arethen distributed to the data capturer, and the process returns to thebeginning of the loop in step 601 to process the next documentationevent. When all of the documentation events in the applicable range havebeen processed, the process continues in step 605 where the datacapturer collects/records images and textual data per the documentationdata acquisition instructions. The data capturer records imagesaccording to the imagery descriptions and the protocols contained in thedata acquisition instructions and typically the recording interfaceprompts the capturer to record additional information associated witheach image. For example, the capturer may be prompted to record whethera construction activity is still “open” or “completed” (such as ifrequested to provide completion verification), augmentation of CSIcodes, additional comments—for example a possible note concerningrequesting immediate notification of observed data, and a notificationtoggle to indicate a request for immediate notification of observeddata. The data capturer may also be prompted to provide additionallocation information and other information such as temperature, humidityand other indications of environmental conditions. In addition to a datacapturer such as a field representative, data capture may also beperformed by remote cameras set in fixed locations during the durationof the project or by other systems or devices. They may be used tobroadcast a live picture as well as being streamed and archived in theDDS data repository for future use. Also, remote sensing devices can beincorporate to automatically capture data that is forwarded (forexample, by streaming) into the DDS data repository directly. Forexample, temperature and humidity sensors can generate dataautomatically and be programmed remotely.

In step 606, the DDS process performs verification on the collecteddocumentation data (images and text), and in step 607, the verifieddocumentation data is uploaded into the DDS data repository for laterretrieval. As described earlier and shown here in step 608, the DDSprocess also detects discrepancies between what is observed in the fieldand the documentation schedule and processes updates to thedocumentation schedule accordingly. This insures that future generationof documentation data acquisition instructions will be accurate to theactual timing and condition of the construction project as it progresses

As described with respect to FIG. 1, once the DDS has uploadeddocumentation data in the form of images and text, various clients(viewers, users, construction personnel and the like) can retrieve andmanipulate images for a variety of uses.

FIGS. 7A-16B are example screen displays of a viewer for viewing,retrieving, and working with documentation data produced by an exampleDirected Documentation System. In one embodiment of a DDS viewer, threedifferent views plus an image view, are available for presenting andmanaging DDS documentation data.

FIGS. 7A-7C are example screen displays of a list view of an exampleDirected Documentation System data viewer. In FIGS. 7A-7C, screendisplay 700 is shown with the tab 701 for list view selected. List viewcan be used to easily select multiple items for treating as a group. Inthe current display 700, a single item 702 is shown as selected. Anexample set of columns is displayed in FIGS. 7A-7C. Some of thesecontain field values that are constrained by the DDS construction dataorganization process and the data acquisition process to include thecommon and project-specific terminology selected typically in thebeginning of the project. For example, the values of the locationsfields 703 and 704, the level field 705, and the orientation field 706are constrained to use uniform terminology. These constraints helpinsure that the selective retrievability of documentation data willoperate as expected. The comments field 707 preferably also contains asmuch of the uniform terminology as possible. The shoot 708, image 709,media label 710 and CD image 711 columns create other indices forretrieving and/or identifying an image, and follow a DDS and/orproject-specific conventions. The aerial picture 712 column allowsidentification of other photos, for example “plan” images takenremotely, that are also associated with the current constructionproject. The drawing file link 713 provides a way to associate a drawingfile, for example a pdf drawing, with some image. The user name fields714 provide some means for authorized persons to provide commentsregarding the images. In some embodiments, the DDS automatically detectsand authorizes particular users and tracks user comments with a user idfor the image as long as the image exists. In this manner userannotations can be associated with individuals (e.g., subcontractors)which may assist in the resolution of construction issues. The indexfield 715 is used to assign an image to one or more classifications,which can also assist in conflict resolution, data retrieval, etc. Asshown, an image can be assigned to one of the conventional constructiondisciplines, such as electrical, mechanical, plumbing, or structural,and/or can be assigned as relevant to producing “as-built”documentation. This field may be extended to use CSI codes as well, andis useful for quickly retrieving, sorting, and/or otherwise manipulatingimages. As mentioned earlier, Appendix C contains a list of example CSIcodes. The document reference field 716 provides a reference link tosomething (e.g., a group “tag”) that relates one or more images. Forexample, a change order may be a common source for a set ofdocumentation images. Also, users may be permitted to assign userdefined group tags to images. Drawing field 717 is a reference link to alocation on a construction drawing that is typically part of thecontract data. It can be another useful way to select images forretrieval.

FIGS. 8A-8B are example screen displays of a detail view of an exampleDirected Documentation System data viewer. Detail view provides detailsof the DDS documentation records associated with documentation data(images and text) for a set of items that have been selected (forexample using selection view to find items by specifying searchcriteria). It also provides a way to access the actual image associatedwith a DDS documentation data record. More specifically, display screen800 is shown with the detail view tag 801 selected to initiate detailview. A user can advance and go back to other images in the selecteditem set using the previous and next buttons 802 and 803, respectively.The image associated with the detail record can be displayed byselection of the CD icon 808.

FIG. 8B is an example of an image associated with the DDS documentationdata record shown in FIG. 8A. Image 810 is displayed by default on topof the data record and can be enhanced or further manipulated fromthere. Note that any changes to the image will be saved as a newrevision, in order to preserve the integrity of the documentationprocess for things such as litigation and claims resolution.

FIG. 8A, illustrates some of the accessible data fields in the datarecord associated with the currently selected item. In this case, theimage shown in FIG. 8B is from a hotel (as indicated by location 1 field804) on floors 20-22 (as indicated by “level” field 806). The commentsshown in CDS comments field 809 are comments input by the data captureror during the documentation data input verification process.

Note that several of the location and orientation fields, namely thelocation fields 804-805, the level field contain dropdown indicators aspart of the field. (The reference field and revision field 807 dropdownindicators are for different purposes.) These dropdown indicators areused to provide ways to explore related images, known in the DDS asintelligent (or active) links. The idea is that when a user is perusingan image of a particular aspect of the construction, the user may wishto see what is adjacent to the area the user is viewing, or what otherimages may be related based upon aspects of the construction projectthat encompass what the user is viewing. For example, if the user isobserving a leak in the plumbing structure as shown by water stains in aphoto on a wall in a room, the user may wish to view the plumbingstructures on the other side of the wall, in other adjacent rooms, inthe ceiling, behind the wall, etc. Intelligent links provide access toother ways of accessing images by proximity and enclosure rather than byspecific selection criteria as one might enter in a search if the userknows what he or she is looking for. Hence data exploration activitiesare enhanced.

Although not shown, when a user selects the dropdown indicator of anintelligent link, the DDS data viewer will drop down a list of relatedlocation specifications. The user is then able to select a value fromthe dropdown list to retrieve associated and potentially surroundingimages. Then, when a user selects an item from this list, the relatedimages are displayed. The list may provide alternative designators tothe ones the user is seeing as a value in the field. For example, if thevalue of the location 2 field 805 is typically a room number, then thedrop down associated with the location 2 field 805 may contain grid linenumbers from the construction drawings, a drawing reference range, levelnumbers, etc.

FIG. 9 is an example screen display of a selection view of an exampleDirected Documentation System data viewer. Selection view provides a wayto specify a set of items (documentation data records) to for viewing indetail view. It provides a searching capability based upon valuesentered in search criteria fields. More specifically, display screen 900is shown with the selection view tag 901 selected to initiate selectionview. In one embodiment, a user may enter search criteria values bytyping text into the fields having variable values or by clicking on thewhite labels for a drop down menu displaying all of the data values forthat field. Other fields may be selected as search criteria by markingthem appropriately (turning them on/off). The fields that are availableas search criteria are typically defined at the beginning of the project(e.g., during the directed construction data organization process).

A user can search a project by specifying all fields individually or incombination with other fields. Typically, the most recent selectionparameters are remembered (during the current user session). The searchcriteria currently displayed in FIG. 9 indicate that a search is to beperformed for all documentation data records having the values specifiedin the location 2, location 2, level, drawing, and activity id fields,from Feb. 3, 2005 to Feb. 4, 2005 and having images that relate toarchitectural and structural aspects, and with the comments andannotations fields as indicated. Other fields and values, which are notshown, can be similarly incorporated. For example, environmentalconditions such as temperature and humidity can also be specified assearch criteria. Also, wildcards may be used to specify values.

In one embodiment, the list view as shown in FIGS. 7A-7C preferablydisplays only those data records that match the current search criteria.In other embodiments, the views operate more independently. In thatembodiment, the results of the search (the set of items selected) arevisible in both list view and detail view.

FIG. 10 is an example screen display of a technique for invoking imageview on one or more images selected in list view. When in list view (asshown in FIGS. 7A-7C), a set of items is selected (is active). When auser indicates, for example by right-clicking a button on an inputdevice, the menu 1001 is displayed in display screen 1000. The menu isapplicable to the active items. In FIG. 10, only one item can be seen asactive (item 1002), although others may be indicated elsewhere inportions of the list that cannot currently be seen. As mentioned, the CDicon from detail view can also be used to display images for activeitems.

FIG. 11 is an example screen display of an image displayed in responsereceiving a “show image” command along with the commands available tomanipulate the image. Once an image is displayed such as that shown inimage 1100, for example, using the techniques described with respect toFIG. 10, a menu 1101 is available of commands that can be used toenhance the image, distribute it, mark it up, print it, etc. In oneembodiment, the menu is displayed in response to a user indication suchas by right-clicking a button on an input device.

FIG. 12 is an example screen display of using the Directed DocumentationSystem to communicate suggestions to other personnel working on theconstruction project using the mark-up capabilities. In FIG. 12, image1200 is displayed and a markup toolbar 1201 is presented in response touser selection of “Image Markup” in menu 1101 shown in FIG. 11. Noteagain, that when images are annotated, enhance, or marked up, they arepreferably save as new revisions to preserve the integrity of theoriginal data.

One of the inherent capabilities of the DDS data viewer when a userselects a set of DDS data records through, for example, list view orselection view, is the ability to view multiple images simultaneously.This permits the user to perform side by side analysis of multipleimages which can be valuable to show the history of a particular aspectof the construction, to compare construction methods, analyze problemsby viewing something from multiple directions at the same time, etc.

FIGS. 13A-13B are example screen displays of the multiple imagepresentation capabilities of an example Directed Documentation Systemdata viewer. In FIG. 13A, display screen 1300 shows a set of tiledwindows. Note that the windows used to view multiple images may be tiledor cascaded or arranged according to some other scheme. Window 1301 is asmaller view of the DDS data viewer, where the three images shown in theother windows 1302-1304 can be seen as currently selected as activerecords. As shown, windows 1302-1304 show three different views of asingle location. All of the image manipulation features available on asingle image are available on the images shown in windows 1302-1304 aswell. FIG. 13B shows the same images in windows 1302-1304 but with azoom feature applied to windows 1302 and 1303. Note that material codesand personnel can be identified in the zoomed versions of the imagesshown in windows 1302 and 1303.

One of the image operations available from an example DDS data viewer issemi-automated object measurement. This feature is particularly usefulfor assessing the type and placement of materials, which is critical forclaims negotiations, permit compliance, insurance verification, qualityassurance programs, etc. The ability to verify the exact placement ofmaterials can lead to reduced insurance costs and quick settlements inthe event of a claim for poor workmanship. Whether the structure was orwas not built to contract standards can be proven without destructivetesting of completed buildings.

One embodiment of the DDS data viewer provides a quick measuring tooland a calculated measuring tool. To measure, a user selects a measuringcalibration icon (see third icon 1202 in the menu bar of the displayscreen 1200 in FIG. 12) and a drop down list of the tools is displayed.The user can then select between the two options as needed. The quickmeasuring tool is used for quick or approximate measuring when an objecthaving a known dimension (for example, a construction element such as astud, piling, piece of rebar) is visible in the same approximate(vertical) plane as an object (construction element) to be measured. Thecalculated measuring tool is used to measure objects within a userdefined plane and calculates values adjusted for perspective.

FIGS. 14A-14B are example screen displays of an electronic quickmeasurement tool that can be used to obtain measurements of constructionelements that appear in approximately the same vertical plane as anelement with a known measurement. In FIG. 14A, the user has selected thequick measurement calibration tool to facilitate an image measurement.The user already knows a dimension (measurement) of construction element1402 displayed in screen display 1400, and enters this measurement indialog 1401. This element then is designated a “calibration object.”From the dimension of this calibration object, additional elements canbe measured anywhere along a horizontal vector that emanates from thecalibration object within approximately the same vertical plane as thecalibration object. (Note that “vertical plane” does not imply arequirement of a perpendicular plane that intersects a horizontal plane.The vertical plane is based upon the depicted image.) FIG. 14B shows auser drawn line 1403 corresponding to an element that the user wishes tomeasure (here the clearance between two buildings). The DDS respondswith the corresponding measurement in display 1404. Note that theelement 1403 (the “line”) to be measured occurs in the same verticalplane (approximately) as the calibration object (line 1402). To increaseaccuracy with respect to similar planes, a user can project a guide line(not shown) which displays across the visible image along the path ofthe calibration object. In one embodiment, the guide line shows thecalibration object in a contrasting color.

FIGS. 15A-15I is an example screen display sequence of using anelectronic calculated measurement tool to measure elements that appearwithin a user defined plane adjusted for perspective. The calculatedmeasurement tool allows items such as waterlines to be located from alandmark and measured within a structure after they have been buried inconcrete or behind a wall.

FIG. 15A shows in image 1500 construction structures (pipes etc.)located on a level of a building prior to being covered up. FIG. 15Bshows the same structures, and lines that a user has drawn to indicate auser defined plane. Note that the plane defines a perspective view ofthe structures shown in image 1500. Lines X1, X2, Y1, and Y2 define aperspective plane for the calculated measurement tool. To be able tohave the DDS data view calculated measurements of arbitrary elementswithin the user defined plane, the user needs to indicate knownmeasurements of lines X1, X2, Y1, and Y2 defining that plane.

FIG. 15C shows a dialog window 1501 invoked by the user to enter thedimensions of each line that defines the user-defined plane. The usercan either manually enter the dimension of each line, or can select thequick measurement tool checkboxes 1502 to indicate to the DDS that theuser wishes to invoke the quick measurement tool to calculate thecorresponding line. FIG. 15D is an example screen display of the user ofa quick measurement tool checkbox 1502 to assist in defining theperspective plane. Display window 1503 shows the DDS calculatedmeasurement of line X1.

Once the user has indicated the measurements of the four lines thatdefine the plane, then the DDS automatically calculates and draws aperspective grid to assist the user in indicating elements for whichmeasurements are desired. FIG. 15E is an example screen display of aperspective grid 1504 overlaid on the display image 1500. Note that insome embodiments, the user is able to specify the distance between thegrid lines. Also, in some embodiments, handles on the grid are supplied(not shown) so that the user can resize (shrink and stretch) the gridand the calculation algorithms are adjusted accordingly to account forthe new grid size. In addition, in some embodiments a user can establishthe grid in a smaller, known, area and then expand or project it to alarger area in order to take advantage of known measurements.

Using the perspective grid as an aid, the user can now indicate to themeasurement tool an arbitrary construction element whose dimension isunknown, as long is it lies within the user defined plane. Conventionalmathematical algorithms can be employed to derive the measurement aslong as the element lies within the plane defined by lines X1, X2, Y1,and Y2. FIG. 15F is an example screen display of a line 1505 drawn by auser to estimate the distance between two objects shown in the image1500. FIG. 15G shows the system calculated measurement returned inwindow 1506.

Once a perspective plane has been defined by the user, in someembodiments it is preferably stored by the system so that it isassociated with the structures depicted by the image for future use.(Since it will be invoked on newly captured images, the plane needs tobe associated with landmarks in the imagery depicted by the image, sothat, as long as the new image contains the landmark, the perspectivegrid can be used. Alternatively, if the image is captured in the sameway approximately as before, the grid can be reused as is.) This is aparticularly beneficial feature for measuring additional elements of thedepicted structure even after the depicted structures have been coveredup. For example, FIG. 15H is displaying an image 1507 that depicts thesame construction level after concrete has been poured over thepreviously exposed pipes etc. When the user invokes calculatemeasurement tool now, the DDS data viewer will recognize that there is auser-defined plane available (and retrieve the plane definition) that isassociated with the elevator core (line Y1) and the building perimeter(line X2) and will utilize it to calculate again a perspective grid.FIG. 15I shows the perspective grid 1508 recalculated from a preserveduser defined plane. From this the user can measure hidden objectsknowing where they were located in the image before the depictedstructures were covered up.

As described with respect to FIG. 1, once the DDS has uploadeddocumentation data in the form of images and text, documentation datacan be distributed using a construction documentation data distributionprocess (for example, through distribution component 105 in FIG. 1),both at the request of users and by the DDS automatically. For example,using the image manipulation commands, users can explicitly invokecommands print one or more images along with other documentation datarecord information, such as that shown in the detail view. In addition,users can print canned reports or custom reports through the use oftemplates. Users can also distribute images and other parts of thedocumentation data records electronically, such as by forwarding such toother media, through an email system, or otherwise across a network.These capabilities support the archiving of images as well asdistribution for a variety of other purposes.

In addition to the distribution available to users, the DDS can itselfissue reports on a periodic basis, at determined intervals, atdetermined events, times, or calendar units, or in response to adocumentation event, which, when triggered, causes the system todistribute an appropriate report. As used herein, the term “report”refers to any electronic or hardcopy compilation of the images, imagesand text, or other parts of the documentation data records that can bedistributed electronically and/or on hardcopy.

For example, reports can be automatically triggered by a documentationevent that is associated with a progress payment. Documentation thatprovides evidence that a payment related milestone has been met is easyto produce using the fields that are stored and can be used to indexand/or retrieve documents relating to a particular milestone. Forexample, a structural milestone related to laying all of the rebar in abuilding could produce all images up to a particular date showing therebar activity in the locations of interest. Alternatively, images canbe annotated by the DDS staff to indicate that they are evidence of averification event. Other similar techniques can be used.

Another example report that can be automatically generated by the DDS isa manpower report. Manpower reports are often used to assess and/orestimate cost. They examine how many people were used to perform aparticular activity and over what time period. Since the directeddocumentation data acquisition instructions direct the capture of imagesrelated to people present at any construction activity, the data forsuch reports can be easily generated.

Also, as discussed earlier, custom reports can also be set up to betriggered by a documentation event including verification events. Aspart of the documentation event, the intended recipients can beregistered as well as the distribution method to be used, etc. Thus, itis possible to distribute such reports fully automatically by computersystems that aid in the implementation of the DDS.

One special class of construction documentation that is consideredhighly desirable and difficult to generate reliably are “as built”drawings, also referred to as “as-builts.” “As-built” is an industryterm used to describe an architectural or engineering drawing of how abuilding was constructed or a system was installed. Systems as-builtsare primarily for the benefit of building operators and owners afterconstruction has been completed. Accurate as-builts are critical inmaintenance, repairs and remodel or expansion projects.

In current construction projects, as-builts are typically delivered as adrawing (or CAD file) showing mechanical, electrical and plumbingassemblies installed in a building. Due to the limitations of a twodimensional drawing, these as-builts are schematic representations ofthe systems installed: they represent what is installed and thetermination point (faucet, switch etc), but not the pathway and routingsof the hidden systems. A complex method of laser measurement andphotographic imagery combined and overlaid with CAD drawings exists andcan be used to create relatively accurate models of existinginstallations. However such a system is time consuming, requiressophisticated and costly computer programs and systems, and is costprohibitive for most uses.

As-builts are typically not generated for general construction ofstructure and frame, except to note change orders or contract revisionsto the original drawings. The Directed Documentation System inherentlygenerates as-builts for portions of the structure and frame as well asfor the various electrical, mechanical, and plumbing systems that areconstructed as a natural product of the directed documentation processthat is used. These as-builts can be compiled on an ad-hoc basis orgenerated through reports that select documentation data records basedupon factors such as completed work, “as-built” classification (see forexample, see classification field in selection view shown in FIG. 9)combined with a location or construction subject of interest.

The DDS also supports the ability to direct the documentation dataacquisition process in advance to support the creation of as-builtdocumentation for various systems (and structural components).Specifically, as part of the protocols, all equipment used in mechanicaldrawings are instructed to be captured. Also, the DDS directedconstruction data organization process can explicitly preload locationsof interest for as-builts into the documentation terminology output. Itcan also build documentation events into the documentation calendar toschedule the explicit documentation of these preloaded locations andsystem on an ongoing basis and with special checks to make suredocumentation data is captured just prior to the systems being covered.

The DDS construction verification process also provides virtualtransparency to construction processes and hidden systems—users of theDDS and/or its reports are able to access the historical data associatedwith an imagery location that has been documented, and whosedocumentation includes an image captured when the verification event iscompleted. This construction verification process provides theequivalent of a visual as-built record of specific building spaces. Whenas-built service is requested on a project receiving comprehensivedocumentation, the DDS processes and components will reflect that need.At the end of the project (or at other times), an as-built data file canbe constructed automatically from the DDS documentation data repository.

An as-built record can also be commissioned separately and the DDS canbe programmed to reflect each situation. To note, as-built images caninclude image enhancement features as well.

FIGS. 16A-16B are example screen displays of “as-built” documentationproduced automatically as a result of a Directed Documentation Systemprocess. The display windows 1601-1604 in FIGS. 16A and 16B show theportions of plumbing and electrical systems in a facility prior toinsulation and wall coverage. Both Figures show the same images;however, FIG. 16B uses the “zoom” function available to manipulateimages in order to identify extreme detail. As-built documentation canbe generated to also identify the room or area, wall, system and date ofthe as-built.

The Directed Documentation System can also produce other types ofdocuments and reports. For example, in addition to the as-builts, theDDS can create fully indexed and annotated documents with crossreferenced photographs in digital media and printed format for purposessuch as pre-condition surveys, training, condominium constructionverification, etc. Data can come from the documentation data recordscollected as a natural part of the directed documentation dataacquisition process or from data gathered explicitly for such documents.

For example, the DDS directed data acquisition process can also guidedata capturers in the documentation of existing buildings and areasadjacent to a project to establish a baseline of conditions prior tocommencement of construction. Such documentation can be used to generatea precondition survey, which is typically used to demonstrate compliancewith regulatory requirements of disturbed area restoration, trafficmanagement, confirm or refute damage claims from neighboring properties,etc.

The DDS processes can also be used to generate documentation fortraining materials, bid information such as that based on sequence ofwork or specific task/equipment type, and a variety of otherclient-specific types of documentation.

The DDS directed documentation procedures can also be used to supportcondominium construction verification. There are stringent rules imposedupon condominium developers regarding disclosure, quality, etc. Aseparate data file can be created as part of the documentation scheduleshowing pertinent construction details and as-built status for eachindividual condominium in a development project. Each data file can betransferred to electronic hard medium (CD, DVD) and/or printed in hardcopy. The DDS can be programmed to distribute individual condominiumdata packages to be included with other sales documents and delivered tothe buyer. The DDS also can be programmed to distribute a single projectrecord to the Developer with all data for all condominiums included.Data for condominium verification can be culled from the DDS datarepository as part of the documentation process or acquired specificallyfor this purpose. With such documentation in hand, the developer is ableto meet obligations of disclosure and achieves a measure of legalprotection; the buyer receives assurance of workmanship, details ofhidden construction and a record to facilitate repairs or remodels.

Also, taken collectively, the documentation projects conducted using theDDS inherently create a vast library of construction sequencing,material handling, and construction methodology that can be indexed andretrieved by authorized personnel across all documentation data records.Through the DDS, this material becomes a retrievable asset.

FIG. 17 is an example block diagram of a general purpose computer systemfor practicing embodiments of a computer-assisted Directed DocumentationSystem. The general purpose computer system 1700 may comprise one ormore server and/or client computing systems and may span distributedlocations. In addition, each block shown may represent one or more suchblocks as appropriate to a specific embodiment or may be combined withother blocks. Moreover, the various blocks of the DDS 1710 mayphysically reside on one or more machines, which use standardinterprocess communication mechanisms to communicate with each other.

In the embodiment shown, computer system 1700 comprises a computermemory (“memory”) 1701, a display 1702, a Central Processing Unit(“CPU”) 1703, Input/Output devices 1704, and network connections 1705.One or more of these components may not be included in any oneimplementation. The Directed Documentation System (“DDS”) 1710 is shownresiding in memory 1701. The components of the DDS 1710 preferablyexecute on CPU 1703 and manage the generation and use of constructiondocumentation data, as described in previous figures. Other downloadedcode 1730 and potentially other data repositories, such as datarepository 1720, also reside in the memory 1710, and preferably executeon one or more CPU's 1703. In a typical embodiment, the DDS 1710includes one or more Construction Data Organization Support modules1711, one or more Documentation Data Acquisition Support modules 1714,one or more Documentation Data Retrieval Support modules 1712, a userinterface 1713 and a project construction data and documentation datadata repository 1715.

In an example embodiment, components of the DDS 1710 are implementedusing standard programming techniques. The DDS components 1711-1715 maybe implemented using object-oriented techniques or more monolithicprogramming techniques. In addition, programming interfaces to the datastored as part of the DDS process can be available by standard meanssuch as through C, C++, C#, and Java API and through scripting languagessuch as XML, or through web servers supporting such. The DDS datarepository 1715 is preferably implemented for scalability reasons as adatabase system rather than as a text file, however any method forstoring such information may be used. In addition, the adjustments to bemade to the contract data and/or documentation schedule may beimplemented as stored procedures, or methods attached to contract data“objects” and documentation schedule “objects” although other techniquesare equally effective.

The DDS 1710 may be implemented in a distributed environment that iscomprised of multiple, even heterogeneous, computer systems andnetworks. For example, in one embodiment, the construction dataorganization support module 1711, the data acquisition support module1714, and the DDS data repository 1715 are all located in physicallydifferent computer systems. In another embodiment, various components ofthe DDS initials 1710 are hosted each on a separate server machine andmay be remotely located from the tables which are stored in the DDS datarepository 1715. Different configurations and locations of programs anddata are contemplated for use with techniques of described herein. Inexample embodiments, these components may execute concurrently andasynchronously; thus the components may communicate using well-known orproprietary message passing techniques. Equivalent synchronousembodiments are also supported by an DDS implementation. Also, othersteps could be implemented for each routine, and in different orders,and in different routines, yet still achieve the functions of the DDS.

All of the above U.S. patents, U.S. patent application publications,U.S. patent applications, foreign patents, foreign patent applicationsand non-patent publications referred to in this specification and/orlisted in the Application Data Sheet, including but not limited AttorneyDocket No. 260168.401 (Express Mail No. EV447227215US), entitled “Methodand System for Directed Documentation of Construction Projects,” filedMar. 13, 2006; and U.S. Provisional Patent Application No. 60/661,048,entitled “Method and System for Directed Documentation for ConstructionProjects,” filed Mar. 11, 2005, are incorporated herein by reference, inits entirety.

From the foregoing it will be appreciated that, although specificembodiments have been described herein for purposes of illustration,various modifications may be made without deviating from the spirit andscope of the present disclosure. For example, the methods and systemsfor performing directed documentation of construction projects discussedherein are applicable to other types of systems and processes that couldbenefit from directed documentation. For example, the directeddocumentation techniques could be applied to plant (e.g., manufacturingplant) equipment and machinery; boat/ship building; status reports forsophisticated manufacturing plants such as steel mills, integratedcircuit chip manufacturing plants, power plants, etc; status reports forenvironmental conditions such as post natural disaster, species/habitstudies, and natural resources; and asset management control. Also, themethods and systems discussed herein are applicable to differingsoftware and hardware architectures, application specific protocols,communication media (optical, wireless, cable, etc.) and devices (suchas wireless handsets, electronic organizers, personal digitalassistants, portable email machines, game machines, pagers, navigationdevices such as GPS receivers, etc.).

1. A method for computer-assisted directing of documentation of aconstruction project, including multi-disciplinary aspects of theconstruction, comprising: storing in a computer system a plurality ofcontract document data, including data from construction drawings,construction specifications, documents indicating changes toconstruction, and a construction schedule for the entire constructionproject; generating and storing in the computer system a documentationschedule that takes into account the stored contract document data; inaccordance with the stored documentation schedule and the contractdocument data, generating and publishing data acquisition instructionsfor a plurality of construction activities to be documented;electronically receiving documentation data that documents eachconstruction activity in accordance with the data acquisitioninstructions as a plurality of images and text; and determining from thereceived documentation data the current progress of each constructionactivity and updating the stored documentation schedule in accordancewith the determined current progress of each construction activity suchthat subsequently generated data acquisition instructions are generatedin accordance with the updated documentation schedule.
 2. The method ofclaim 1, further comprising: updating the contract document data toinclude received indications of construction changes such thatsubsequently generated data acquisition instructions are generated inaccordance with the updated contract documents.
 3. The method of claim 1wherein the data acquisition instructions include descriptions thatinstruct how to document a plurality of aspects of each constructionactivity.
 4. The method of claim 1 wherein the data acquisitioninstructions for the plurality of construction activities to bedocumented further include documentation protocols that indicate furtheropportunities for documentation data acquisition.
 5. The method of claim4 wherein the documentation protocols regard at least one of industryknowledge and guidelines, construction activity, equipment types, siteconditions, people, material, quality, or safety.
 6. The method of claim1, further comprising: generating and storing in the computer system aset of project-specific terminology for use in documenting theconstruction project in a uniform manner; and generating and publishingthe data acquisition instructions using the project-specificterminology.
 7. The method of claim 1, further comprising: determiningand storing in the computer system a set of documentation protocols andterminology for the construction project; and generating the dataacquisition instructions to include a portion of the determinedprotocols and consistent with determined terminology so that receiveddocumentation data is uniform across the construction project.
 8. Themethod of claim 1, further comprising: integrating the receiveddocumentation data into a plurality of retrievable images that providehistorical documentation of the construction project.
 9. The method ofclaim 1, further comprising: integrating the received documentation datainto a plurality of retrievable images that provide near real-timedocumentation of the construction project.
 10. The method of claim 1further comprising: verifying the received documentation data; andintegrating the verified documentation data into a plurality ofretrievable images that provide documentation of the constructionproject.
 11. The method of claim 10 wherein the verifying the receiveddocumentation data comprises: enhancing an image; and modifyingdescriptions associated with the image as necessary to be consistentwith what the image shows.
 12. The method of claim 11, furthercomprising: confirming that a scheduled event is associated with an openor closed status.
 13. The method of claim 1, further comprising:automatically generating progress payment reports that reflect progressof construction activities.
 14. The method of claim 13 wherein theautomatically generating progress payment reports is triggered by anevent scheduled in the documentation data schedule.
 15. The method ofclaim 13, further comprising: automatically communicating the generatedprogress payment reports by electronic means.
 16. The method of claim 1,further comprising: at a determined time, automatically generating areport that contains documentation data that documents progress and/oraspects of the construction project.
 17. The method of claim 16 whereinthe determined time is a time interval, a predetermined time, acalculated time, based upon a calendared event, or in response to arequest.
 18. The method of claim 16 wherein the report documents atleast one of project progress, aspects of the construction project, orparticular features of the construction being built.
 19. The method ofclaim 16, further comprising: automatically communicating the generatedprogress payment reports by electronic means.
 20. The method of claim 1,further comprising: integrating the received documentation data into aplurality of retrievable images that provide documentation of theconstruction project over a period of time; receiving a request toretrieve and display at least one of the retrievable images based upon aconstruction-related selection criteria; and displaying at least oneimage in response to the received request.
 21. The method of claim 20wherein a plurality of images are displayed in response to the requestand further comprising: displaying a first one of the plurality ofimages and a second one of the plurality of images approximatelysimultaneously such that a viewer can view both images at the same timeand manipulate each image independently.
 22. The method of claim 21wherein the first image represents a structure of the constructionproject at a first time and the second image represents the structure ata second time allowing the structure to be analyzed over a time periodthat includes the first time and second time.
 23. The method of claim 21wherein the first image represents a system of the construction projectat a first time and the second image represents the system at a secondtime allowing the system to be analyzed over a time period that includesthe first time and second time.
 24. The method of claim 23 wherein thesystem is an aspect of an electrical, plumbing, or mechanical system.25. The method of claim 21 wherein the manipulation comprises a zoomingoperation.
 26. The method of claim 21 wherein the first image shows afirst subject of the construction project and the second image shows asecond subject that is not the same as the first subject, yet the imagesare both associated with a same contract document.
 27. The method ofclaim 20, the displayed at least one image associated with ageographical area, and further comprising: displaying a linked fieldassociated with the displayed at least one image such that, uponselection of a value of the linked field, automatically displaying atleast one related image from a related geographical area thatencompasses, surrounds, or is in proximity to the geographical areaassociated with the displayed at least one image.
 28. The method ofclaim 27 wherein the related geographical area is defined by at leastone of a grid location, a level, a room, or a reference to a contractdrawing or specification.
 29. The method of claim 27 wherein the linkedfield is used to specify the geographical area that encompasses,surrounds or is in proximity to the geographical area associated withthe displayed at least one image.
 30. The method of claim 20, thedisplayed at least one image associated with a group, and furthercomprising: displaying a linked field associated with the displayed atleast one image such that, upon selection of a value of the linkedfield, automatically displaying at least one related image from arelated group that is associated with or is the same as the groupassociated with the displayed at least one image.
 31. The method of 30wherein the related group is defined by at least one of a reference tag,a change indication document, or a construction subject area, or areference to a CSI category or subcategory.
 32. The method of claim 30wherein the linked field is used to specify the related group that isassociated with or is the same as the group associated with thedisplayed at least one image.
 33. The method of claim 1, furthercomprising: integrating the received documentation data into a pluralityof retrievable images that provide “as-built” documentation of theconstruction project.
 34. The method of claim 33 wherein the “as-built”documentation comprises “as-built” documentation for structural orframing aspects of the construction project.
 35. The method of claim 33wherein the “as-built” documentation comprises “as-built” documentationfor electrical, mechanical, or plumbing systems constructed by theconstruction project.
 36. A method in a computer system for trackingconstruction to produce “as-built” documentation of a constructionproject, comprising: receiving data from a plurality of constructioncontract documents; during construction of a structure designated by thereceived data from the contract documents, receiving a first dataacquisition image that represents the structure relative to a firstperiod of time and a second data acquisition image that represents thestructure relative to a second period of time; and automaticallycreating “as-built” documentation for the structure from the first imageand the second image such that, when the construction of the structureis completed, the first and second images provide a record of systemsand/or structures that have been installed as part of the resultantstructure.
 37. The method of claim 36 wherein the automatically creatingthe “as-built” documentation further comprises: automatically creating“as-built” documentation for the structure from the first image and thesecond image, wherein an internal feature of the structure that is nolonger observable is shown in at least one of the images.
 38. The methodof claim 36 wherein the images are used to show hidden systems behind acovered or closed structure.
 39. The method of claim 38 wherein thehidden systems comprise plumbing, mechanical, fire protection, orelectrical systems.
 40. The method of claim 36 wherein the “as-built”documentation is used to provide information for future maintenance. 41.The method of claim 36 wherein the “as-built” documentation is used toprovide information for at least one of later expansion or renovation.42. A method in a computer system for producing documentation ofconstruction methodologies for a plurality of construction projects,comprising: receiving data from a plurality of construction contractdocuments for the plurality of construction projects; duringconstruction of at least one structure as part of one of theconstruction projects, receiving a plurality of data acquisition imagesthat represent the structure relative to different periods of time; andfrom the received images, automatically creating a library ofconstruction methodologies that can be indexed and retrieved across theplurality of construction projects.
 43. The method of claim 42 whereinthe construction methodologies includes construction sequencing andmaterial handling information.
 44. A method in a computer system formeasuring construction elements displayed in electronic images thatdocument a construction project, comprising: retrieving and displayingan image that shows a construction structure or a construction system ina portion of the construction project; receiving a first measurement ofa known element in the structure or system shown in the displayed image;storing the received first measurement of the known element as acalibration measure; receiving a user selection of a first constructionelement in the displayed image that is to be measured, the firstconstruction element having an unknown dimension; using the calibrationmeasure to automatically calculate the dimension of the firstconstruction element; and displaying the calculated dimension.
 45. Themethod of claim 44 wherein the known element and the first constructionelement that is to be measured are located in approximately the samevertical plane as a vertical plane that encompasses the known elementshown in the displayed image.
 46. The method of claim 44 wherein theusing the calibration measure to automatically calculate the dimensionis performed in response to receiving an indication that a calibrationtool from a toolbar has been selected.
 47. The method of claim 44,further comprising: using the calibration measure to automaticallycalculate the dimension of a second, a third, and a fourth constructionelement, wherein the first, second, third, and fourth constructionselements together define a perspective plane; displaying a perspectivegrid to illustrate the perspective plane; receiving an indication ofanother construction element located within the perspective plane thathas an unknown dimension; automatically calculating the unknowndimension of the another construction element located within theperspective plane.
 48. The method of claim 47, further comprising:receiving an indication of size of grid lines to be displayed in theperspective grid; and displaying the perspective grid according to theindicated size.
 49. The method of claim 47, further comprising:receiving an indication that the perspective grid has been resized to anew size; recalculating the perspective plane according to the new size;redisplaying the image according to the new size; and displaying a newperspective grid according to the recalculated perspective plane.